You put a lot of work into the Store page, you should link it here!

Just for consistencies sake, I would try to leave a newline between each selector and block. It makes things slightly easier to read

Here, rather than having two flex boxes as separated containers, I would put them inside a container of their own. You could then have a separate class for each image with descriptive text that would make it easier to centre.

Often there are a lot of flex boxes within flexboxes within flexboxes, and it all starts to get like the plot of Inception, but it makes things like centering content significantly simpler (you can certainly also use a grid for this too)

<!-- The code could look something like this (without the nasty inline styling!) -->
<div style="display: flex;">
  <p>Everyone needs a little Karma.</p>
  <div style="display: flex;">
    <div style="display: flex; flex-direction: column; align-items: centre;">
      <img alt="icon devices" src="/img/icon-devices.svg " />
      <p>Internet for all devices</p>
    </div>
    <!-- Insert the two other images with descriptions here -->
  </div>
</div>

This would solve your alignment issues on the images with text beneath quite nicely, and generally it's neater to group things together in the code that are grouped together in the user interface itself. This is particularly useful when we use semantic HTML, as it's good for accessibility to enclose all of the content for an article (which each of those three images/descriptions should arguably be) within the semantic HTML itself.

I would take a look at the HTML/CSS style guide: https://www.w3schools.com/html/html5_syntax.asp

You can get formatting tools that handle this for you, and these things tend to only be guidelines rather than hard and fast rules, but I've not encountered formatting like this in the wild!

VS Editor does it automatically when i save. I will keep a look to avoid it. THANK YOU

We use links to redirect our users to different pages, and buttons for user actions (more to be covered when we step into the wonderful world of JavaScript). Combining them both isn't best practice for accessibility or user experience.

Really good use semantic HTML throughout this

Variable names are pretty important, can you be more descriptive than container3? Remember to write code that someone in six months will have to read and change.

Great to see the reusability of your CSS classes here.

I would be careful here, as applying situational values to a class generically called 'flex' could lead to bad situations. I would just apply the rule of display: flex; in a class like this, and maybe have a variant of this class that applies a column.

There are loads of methodologies that you can use to structure your CSS to keep it clean and reusable, particularly at scale. BEM is one of them: https://getbem.com/introduction/ This is a lot to take in at the m

Great consistent usage of alt tags here, a really good habit to get into.